Method and system for context aware scheduling of resources

ABSTRACT

Embodiments herein provide a method and a system for context aware scheduling of resources. The method includes performing a cell search in based on a context database, the context database including temporal parameters, location parameters and network parameters, identifying a first cell corresponding to the network parameters in the database based on the cell search, and performing a connected mode procedure with the identified first cell.

CROSS-REFERENCE TO RELATED APPLICATION(S)

This application claims priority under 35 U.S.C. § 119 (a) to an IndianProvisional Patent Application filed on May 11, 2015 in the IndianIntellectual Property Office and assigned Serial No. 2383/CHE/2015, andan Indian Complete Patent Application filed on May 10, 2016 in theIndian Intellectual Property Office and assigned Serial No.2383/CHE/2015, the entire contents of each of which are incorporatedherein by reference.

TECHNICAL FIELD

The embodiments herein generally relate to Machine-type communication(MTC) device with wireless communication network. More particularly,related to a mechanism for context aware scheduling of resources.

BACKGROUND

Machine-type communication (MTC)/Machine to Machine (M2M) communicationis advancing rapidly. The MTC communication facilitates a directcommunication (requiring seldom human-machine interaction) with one ormore MTC/M2M device(s) deployed therein. The MTC/M2M devices, (i.e.,Internet of Things (IoT) device, wireless transmit/receive units(WTRUs)) are based on 3 GPP/cellular based protocols, with intention ofsaving power and reduce congestion in a network. These MTC/M2M deviceuse radio access channels (i.e., communication channel) in compliancewith the same protocol (i.e., 3 GPP, cellular network procedure) used bymobile device(s) to connect to a network. As a result, the cellular(IoT) networks designed for generic use cases brings in-efficiencies inresource allocation and adds overhead in a wireless communicationsystem.

These M2M/MTC/IoT enables three major use cases such as command-responsetraffic (triggered reporting), having latency of 10 seconds, exceptionreported by IoT devices having latency of 3-5 seconds and periodicreports or keep alive. The IoT devices are use case centric (to solve aspecific problem) and not for general purpose like smartphones/mobiles.A generic protocol design leaves sub optimal choices for a specific usecase. However, optimizations are not designed based on scenarios andother use cases for M2M devices.

The above information is presented as background information only tohelp the reader to understand the present invention. Applicants havemade no determination and make no assertion as to whether any of theabove might be applicable as Prior Art with regard to the presentapplication.

SUMMARY

The principal object of the embodiments herein is to provide a mechanismfor context aware scheduling of resources.

Another object of the embodiments herein is to provide a mechanism forcreating a context database including temporal parameters, locationparameters and network parameters acquired for a period of time(historically).

Another object of the embodiments herein is to provide a mechanism forinitiating a cell search in an ultra-deep-sleep mode based on thetemporal parameters, the location parameters and the network parameters.

Another object of the embodiments herein is to provide a mechanism foridentifying a cell corresponding to the network parameters in thedatabase based on the cell search.

Another object of the embodiments herein is to provide a mechanism forinitiating a connected mode procedure with the identified cell.

Another object of the embodiments herein is to provide a mechanism ofhandling emergency condition by the MTC device and the cell.

Another object of the embodiments herein is to provide a mechanism toinitiate creation of groups of MTC devices based on information such asnumber of reports generated for a time period and/or average durationbetween each generated report.

Another object of the embodiments herein is to provide a mechanism forcreating groups by aggregating each MTC device in each of the groupbased on the information.

Another object of the embodiments herein is to provide a mechanism forindicating resource allocation to at least one MTC device within a groupthrough a Machine Type Semi Persistence Scheduling-Physical DownlinkControl Channel (PDCCH) (M-SPS-PDCCH) in an M-SPS interval to transmitUL data to the cell.

Accordingly the embodiments herein provide a method and system forcontext aware scheduling of resources. The method includes creating acontext database including temporal parameters, location parameters andnetwork parameters acquired for a period of time. Further, the methodincludes initiating a cell search in an ultra-deep-sleep mode based onthe temporal parameters, the location parameters and the networkparameters. Further, the method includes identifying a cellcorresponding to the network parameters in the database based on thecell search. Furthermore, the method includes initiating a connectedmode procedure with the identified cell.

In an embodiment, the method further includes synchronizing with a cellother than the identified cell; registering with the cell; andtransitioning to a connected mode.

In an embodiment, the network parameters includes a Public Land MobileNetwork (PLMN), a Radio Access Technology (RAT), a Timing Alignment(TA), a Uplink (UL)-Transmission (Tx) Power, a Physical Uplink SharedChannel (PUSCH) power and a Physical Uplink Control Channel (PUCCH)power.

In an embodiment, the method further includes sharing context ID,associated with the temporal parameters, the location parameters and thenetwork parameters, present in the context database to the cell.

In an embodiment, the method further includes joining a group created bythe cell for scheduling the UL data through Machine Type SemiPersistence Scheduling-Physical Downlink Control Channel (M-SPS-PDCCH)interval; identifying SPS resources allocated for MTC device within thegroup and transmitting UL data to the cell in the identified SPSresources.

In an embodiment, transmitting the UL data to the cell includesestimating downlink (DL) channel compensation and transmitting the ULdata when the estimated DL channel compensation exceeds a predefinedthreshold.

In an embodiment, the method further includes dynamically updating thecontext database with the temporal parameters, the location parametersand the network parameters in response to determining that the UL datatransmission is failed; and determining a cell other than the previouslyidentified cell for synchronization.

In an embodiment, the method further includes determining a suspendedstate and indicating the suspend state to the identified cell in PUCCH,where the suspend state suspends allocation of resources by M-SPS-PDCCHfor the MTC device.

In an embodiment, the method further includes determining a resumestate; determining a current cell, where MTC device has to resume;indicating the resume state in PUCCH to the current cell, where thecurrent cell is other than the cell where the MTC device suspended andthe context database is available with all the cells, originally presentin the context database, through internal network message exchange; andreceiving resources from the current cell.

In an embodiment, where the resume state is indicated implicitly when atimer is expired, where the timer value is a predefined threshold periodindicated in the suspend message.

Accordingly the embodiments herein provide a method and system forcontext aware scheduling of resources. The method includes indicating,by the MTC device, an emergency condition to the cell and allocating, bythe cell, uplink (UL) resources with predefined conditions.

In an embodiment, the predefined conditions are maximum redundancy,minimum modulation, and time diversity.

In an embodiment, indicating the emergency condition includes minimizinga sounding reference signal (SRS) power.

In an embodiment, allocating the UL resources includes establishing alogical link entity catering to the emergency data between the cell andthe MTC device.

Accordingly the embodiments herein provide a method and system forcontext aware scheduling of resources. The method includes receivinginformation from a plurality of MTC devices. The information comprises anumber of reports generated for a time period and/or average durationbetween each generated report. The method includes creating groups byaggregating each MTC device in each of the group based on theinformation. Further, the method includes indicating resource allocationto at least one MTC device within a group through a Machine Type SemiPersistence Scheduling-Physical Downlink Control Channel (PDCCH)(M-SPS-PDCCH) in M-SPS interval to transmit UL data to the cell.

In an embodiment, allocating the M-SPS-PDCCH resources in the M-SPSinterval to each the group is in response to determining that load inthe cell is below a threshold.

These and other aspects of the embodiments herein will be betterappreciated and understood when considered in conjunction with thefollowing description and the accompanying drawings. It should beunderstood, however, that the following descriptions, while indicatingpreferred embodiments and numerous specific details thereof, are givenby way of illustration and not of limitation. Many changes andmodifications may be made within the scope of the embodiments hereinwithout departing from the spirit thereof, and the embodiments hereininclude all such modifications.

BRIEF DESCRIPTION OF THE DRAWINGS

This invention is illustrated in the accompanying drawings, throughoutwhich like reference letters indicate corresponding parts in the variousfigures. The embodiments herein will be better understood from thefollowing description with reference to the drawings, in which:

FIG. 1 shows an overview of a system for context aware scheduling ofresources, according to an embodiment as disclosed herein;

FIG. 2a is a flow diagram illustrating a method of sharing contextdatabase by a MTC device and applying context information based on anidentified cell, according to an embodiment as disclosed herein;

FIG. 2b is a flow diagram illustrating a method of transitioning to aconnected mode from an ultra-deep-sleep mode by a MTC device, accordingto an embodiment as disclosed herein;

FIG. 2c is a flow diagram illustrating a method of dynamically updatingcontext database, according to an embodiment as disclosed herein;

FIG. 3 is a flow diagram illustrating a method for context awarescheduling of resources during emergency condition, according to anembodiment as disclosed herein;

FIG. 4 is a flow diagram illustrating a method for context awarescheduling of resources to at least one MTC device is a group, accordingto an embodiment as disclosed herein;

FIGS. 5a-5b illustrates M-SPS-PDCCH based scheduling of resources for agroup of MTC devices with variable SPS interval, according to anembodiment as disclosed herein;

FIG. 6 is a sequence diagram depicting various signaling messagesbetween a MTC device and a cell for context aware scheduling ofresources, according to an embodiment as disclosed herein;

FIG. 7 is a sequence diagram depicting various signaling messagesbetween a MTC device and one or more cells for context aware schedulingof resources, according to an embodiment as disclosed herein;

FIG. 8 is a sequence diagram depicting various signaling messagesbetween a MTC device and a cell for handling emergency conditions,according to an embodiment as disclosed herein; and

FIG. 9 is a sequence diagram depicting various signaling messagesbetween a MTC device and a cell for handling emergency condition,according to an embodiment as disclosed herein.

DETAILED DESCRIPTION

The embodiments herein and the various features and advantageous detailsthereof are explained more fully with reference to the non-limitingembodiments that are illustrated in the accompanying drawings anddetailed in the following description. Descriptions of well-knowncomponents and processing techniques are omitted so as to notunnecessarily obscure the embodiments herein. Also, the variousembodiments described herein are not necessarily mutually exclusive, assome embodiments can be combined with one or more other embodiments toform new embodiments. The term “or” as used herein, refers to anon-exclusive or, unless otherwise indicated. The examples used hereinare intended merely to facilitate an understanding of ways in which theembodiments herein can be practiced and to further enable those skilledin the art to practice the embodiments herein. Accordingly, the examplesshould not be construed as limiting the scope of the embodiments herein.

Prior to describing the invention in detail the definition of the termis mentioned below.

Ultra-Deep-Sleep mode: Refers to a state which is not a standardizedstate, it means that the device will get into power down mode, and noteven listen to Paging and perform measurement, unless there is a wake upfor event reporting triggered by sensor unit (s).

Throughout the description, the terms sensors, sensor unit and sensorhub are used interchangeably.

Throughout the description, the terms network and cell are usedinterchangeably.

Accordingly the embodiments herein provide a method and system forcontext aware scheduling of resources. The method includes creating acontext database including temporal parameters, location parameters andnetwork parameters acquired for a period of time (historically).Further, the method includes initiating a cell search in anultra-deep-sleep mode based on the temporal parameters, the locationparameters and the network parameters. Further, the method includesidentifying a cell corresponding to the network parameters in thedatabase based on the cell search. Furthermore, the method includesinitiating a connected mode procedure with the identified cell.

Accordingly the embodiments herein provide a method for a method andsystem for context aware scheduling of resources. The method includesindicating, by the MTC device, an emergency condition to the cell andallocating, by the cell, uplink (UL) resources with maximum redundancy,minimum modulation, and time diversity.

Accordingly the embodiments herein provide a method and system forcontext aware scheduling of resources. The method includes receivinginformation from a plurality of MTC devices, wherein the informationcomprises at least one of a number of reports generated for a timeperiod and average duration between each generated report. The methodincludes creating groups by aggregating each MTC device in each of thegroup based on the information. Further, the method includes indicatingresource allocation to at least one MTC device within a group through aMachine Type Semi Persistence Scheduling-Physical Downlink ControlChannel (PDCCH) (M-SPS-PDCCH) in the M-SPS interval to transmit UL datato the cell.

In an embodiment, allocating the M-SPS-PDCCH resources in the M-SPSinterval to each the group in response to determining that load in thecell is below a threshold.

Unlike the conventional systems and methods, where the network isbroadly generic, for e.g., allocating resources to various applicationsinstalled in the mobile device, the proposed M2M network protocol isspecific to the event triggered by the MTC device (use case centric suchas exceptional and periodic).

Accordingly the embodiments herein provides a mechanism for designingM2M protocol for a mobile originating (MO) only device/wearable devicewhich is based on uploading of the data from the device to the M2Mserver based on events triggered from a sensor unit at the MTC device.For example activity trackers, for children or sports/fitness use cases.These specific use cases, does not require mobile terminating callscenarios, thus a lot of idle mode procedures can be disabled, andleaves a thin Mobile originated procedure, with other relatedoptimizations.

The MTC device can attempt a MO call when it detects an event from thesensor unit to trigger the MO call. The event can be categorized undertwo broad scenarios such as normal and emergency. The detection can bebased on the sensor inputs which are directly interfaced with a callinitiation module in the M2M/MTC device architecture.

Unlike the conventional systems and methods, the proposed cell whileallocating the resources understands the current case (use case) of theMTC device and allocates resources accordingly.

Unlike the conventional systems and methods, the proposed mechanismimproves the standby battery life of the MTC device by removal ofDiscontinuous Reception (DRX) and cell re-selection procedure, whichenables huge power saving in idle mode as the MTC device goes to theUltra-Deep-Sleep mode and turns OFF its modem/RF/processor.

Referring now to the drawings, and more particularly to FIGS. 1 through9, where similar reference characters denote corresponding featuresconsistently throughout the figures, there are shown preferredembodiments.

FIG. 1 shows an overview of a system 100 for context aware scheduling ofresources, according to an embodiment as disclosed herein. The system100 includes one or more MTC devices (102 a-102 n, hereinafter “102”)communicating with a cell 104. In an embodiment, the MTC device 102includes a sensor unit configured to detect the events such as smokedetection, emergency metering, activity tracker detection, or the like.

In an embodiment, the MTC device 102 are Internet of Things (IoT)devices such as activity trackers, sensors, wireless transmit/receiveunits (WTRUs) or the like.

In an embodiment, the cell 104 is an eNodeB (eNB), a Base station (BS)deployed in a network.

A Servicing Network Gateway (SGW) provides a connection to the PacketData Network Gateway (PGW), which in turn provides a connection to acontext database 103 (for example, stored in a MTC tracking server)created by the MTC device 102. The context database 103 encompasses thecontext aware parameters associated with the MTC device 102 that wascreated by the MTC device 102 for a period of time in theUltra-Deep-Sleep mode.

Unlike the conventional systems and methods, the cell 104 acquisition(camping onto the network) by the MTC device 104 from theUltra-Deep-Sleep mode (for e.g., the idle mode) is fast, by virtue ofthe context database 103.

For example, considering the mere fact that the MTC device 102 such asactivity trackers, emergency modules follows the specific patterns suchas consistently operating (accessing the cell 104) from same premises,same location, same time interval, or the like. The MTC device 102accessing the network during these scenarios can be profiled, forexample, which network (or cell 104) that the MTC device 102 may campon, the network access parameters, the location parameters and thetemporal parameters applied to access the network.

These profiles can form a context for the MTC device 102. Thus everytime the MTC device 102 accesses the network, based on the context (timeand/or location), a cell search is performed and results in for thefaster connection to the cell. The context is based on a historicalacquisition of temporal parameters and location parameters. Further,context ID is created against the temporal parameters and the locationparameters.

The context database 103 includes the temporal parameters such as thetime at which the MTC device 102 access the cell 104. Further thecontext database 103 includes location parameters such as GPScoordinates of the MTC device 102 while accessing the cell 104 at thetime instance. Furthermore the context database 103 includes the networkparameters such as the PLMN, the RAT, the TA, the UL-Tx Power, the PUSCHpower, the PUCCH power, or the like (as shown in the Table. 1).

TABLE 1 Time Location Context (Mandatory) (optional) Network #1 T = T1 L= L1 {Cell-1, PLMN-1, RAT-1, TA-1, UL-TxPow-1, PUSCH_pow-1, PUCCH_pow-1}#2 T = T2 L = L2 {Cell-2, PLMN-2, RAT-2, TA-2, UL-TxPow-2, PUSCH_pow-2,PUCCH_pow-2} # . . . # . . . N T = Tn L = Ln {Cell-n, PLMN-n, RAT-n,TA-n, UL-TxPow-n, PUSCH_pow-n, PUCCH_pow-n}

Unlike the conventional systems and methods, where the context basedsearch was performed based on location and limited network parameters(such as the PLMN and the RAT) only, the proposed context based searchfor the network, using the context database 103, by the MTC device 102includes the temporal parameters, the network parameters such inaccordance with the Cell, PLMN and RAT, the parameters includes (TA,UL-Tx Pow, PUSCH_pow, and PUCCH_pow).

Unlike the conventional systems and methods, the proposed methodprovides a use case specific/context aware network in order to optimizethe network for the MTC device 102 in the exception reporting by havinglatency of 3-5 seconds and periodic reports or Keep alive, insensitiveto latency.

For example, kids usually have some pre-defined places, where they go asper their regular schedule, e.g. Park, Day care, School, home, friend'shouse. It can be inferred, that the kids context can be associated withthe cellular connectivity, e.g. based on (Time, Location, activity)consequently association of the cell can be predicted with coarse levelaccuracy.

The reports transmitted by the MTC device 102 can be, for e.g.,classified as (a) “Delay tolerant Mobile originated (MO) data” (usecase-Periodic reports) (b) “Emergency information data (usecase-Emergency reported).

In an embodiment, the Periodic measurement reports, where the MTC devicecontinue transmitting the measurements at periodic interval of time. Fore.g., temperature reports, meter reading, reports generated from theactivity trackers, or the like. In an embodiment, for e.g., theemergency reporting by the MTC device 102 can include transmitting theemergency measurements such as fire alert, smoke detection, with nolatency.

In an embodiment, with the required network support, the MTC device 102can only attach once with the network, negotiate all security,capability and configuration parameters and thereafter it can beattached to the network, even though it shuts off its modem/RF. Thus theMTC device 102 context remains alive in the core network, even though itis never paged or doing periodic location/tracking area update, forwhich the MTC device 102 informs that its mode of operation isMTC-Mobile Originated (MO) communication.

In an embodiment, the cell 104 can configured to receive the contextdatabase 103 associated with the MTC device 102. In an embodiment,during the MTC device 102 accessing the neighboring the cells 106 and108, a Handover of the context database 103 can be performed by the cell104 to the one or more neighboring cells 104 a, 104 b . . . 104 n. Thus,the context database 104 can be dynamically updated whenever the MTCdevice 102 camps on to the neighboring cells 106 and 108.

In an embodiment, the MTC device 102 connects to the network, from theUltra-Deep-Sleep mode upon camping onto the cell 104, the operations ofthe MTC device in the connected mode is detailed below.

Connected mode (Specific to Emergency Service for MO-only devices): TheMTC device 102 in the connected mode can be configured to transmit thereport in case of the emergency services, where the communicationbetween the MTC device 102 and the cell 104 is highly reliable and withminimum latency. Thus, a cross layer optimization is triggered where theMTC device 102 can be configured to trigger the UL data with highlyreliable Radio link entity. The latency can be minimized by providingrobust resource allocation for radio link, thereby minimizing the needof retransmission, as detailed in conjunction with FIG. 8

The FIG. 1 shows the system 100 but it is to be understood that otherembodiments are not limited thereon. In other embodiments, the system100 may include less or more number of components. Further, the labelsor names of the components are used only for illustrative purpose anddoes not limit the scope of the invention. One or more components can becombined together to perform same or substantially similar function inthe system 100.

FIG. 2a is a flow diagram illustrating a method 200 a of sharing contextdatabase by a MTC device and applying context information based on anidentified cell, according to an embodiment as disclosed herein. In anembodiment, when the MTC device 102 is switched “ON” the MTC device 102initiates the network search procedure where the modem/RF/processor ofthe MTC device 102 request for the resources, cellular (3GPP) networkprocedure.

3GPP cell search procedure: In an embodiment, the method 200 a includesinitializing the cell search (cell 104 or neighboring cells 106 and108.) as per the 3GPP (cellular) search procedure. In an embodiment, themethod 200 a allows the MTC device 102 to initialize the cell search asper the 3GPP (cellular) search procedure.

Further, the method 200 a includes saving the temporal parameters andthe location parameters (time, location, activity level-sync-context).In an embodiment, the method 200 a allows the MTC device 102 to save(time, location, activity level-sync-context) acquired for a period oftime.

Further, the method 200 a includes saving the network parameters (RACHpower, timing alignment, PUSCH power, PHR-Conn-context). In anembodiment, the method 200 a allows the MTC device 102 to save thenetwork parameters (RACH power, timing alignment, PUSCH power,PHR-Conn-context).

Further, the method 200 a includes initializing the connected modeoperation procedure (for e.g., registering to the cell identified basedon 3 GPP search procedure). In an embodiment, the method 200 a allowsthe MTC device 102 to initialize the connected mode operation procedure.

Thus, the aforementioned parameters (temporal, location and network) aretracked and stored in the context database 103 of the MTC device 102. Inan embodiment, the MTC device 102 goes into the Ultra-Deep-Sleep mode,where the processor/modem/RF of the MTC device goes into sleep mode(de-allocating the resources). Consequently, the below mentioned steps,of the method 200 a details the functions of the MTC device 102 inacquiring the network (cell 102) and transitioning to the connected mode(for e.g., re-establishment) from the Ultra-Deep-Sleep mode.

In an embodiment, at step 202 a, the method 200 a includes creating thecontext database 103 with the stored temporal parameters, the locationparameters and the network parameters acquired for the period of time(historically). In an embodiment, the method 200 a allows the MTC device102 to create the context database 103 with the temporal parameters, thelocation parameters and the network parameters acquired for the periodof time.

Further, at step 204 a, the method 200 a includes initiating the cellsearch (cell 104 or neighboring cells 106 and 108) based on the temporalparameters, the location parameters and the network parameters. In anembodiment, the method 200 a allows the MTC device 102 to initiate thecell search (in the Ultra-Deep-Sleep mode) based on the temporalparameters, the location parameters and the network parameters.

Further, at step 206 a, the method 200 a includes identifying the cell(cell 104 or neighboring cells 106 and 108.) corresponding to thenetwork parameters in the context database 103 based on the cell search.In an embodiment, the method 200 a allows the MTC device 102 to identifythe cell corresponding to the network parameters in the database basedon the cell search.

If the MTC device 102 identifies that the cell (i.e., cell 104)corresponding to the network parameters (from the context database 103)is available thereon, at step 208 a, the method 200 a includes applyingthe context information, the RACH power, the TA, the Uplink control, thedata channel power, and PHR (power head room info) in order to camp tothe cell (in the connected mode).

Further, at step 210 a, the method 200 a includes determining the statusof the UL transmission. If the UL-Tx fails, the MTC device 102 initiatesthe cell search as per 3GPP search procedure.

If the MTC device 102 identifies that the cell corresponding to thenetwork parameters (from the context database 103) is unavailablethereon, at step 212 a-216 a, the method 200 a includes initializing thecell search (cell 104 or neighboring cells 106 and 108.) as per the 3GPP(cellular) search procedure detailed above.

The various actions, acts, blocks, steps, or the like in the flowdiagram 200A may be performed in the order presented, in a differentorder or simultaneously. Further, in some embodiments, some of theactions, acts, blocks, steps, or the like may be omitted, added,modified, skipped, or the like without departing from the scope of theinvention.

In an embodiment the MTC device 102 can do a normal network attachprocedure on the best cell, and indicate to the cell using attach typemessage identifier, that the MTC device 102 is the MO-only device, typeof device, traffic class, Mobility Type, data size, which can indicateto the network that periodic updates like Tracking area update(TAU)/Routing Area Update (RAU) cannot be performed for the MTC device102, so that the network doesn't mark the MTC device 102 as ‘notreachable’ or ‘switched-off’.

The idle mode procedures like the cell reselections and maintainingN-Cell cannot be present for the MTC device 102. Thus, the MTC device102 maintains a ‘thin’ system information database, and can limitreading and maintaining essential SIB's required for connectionmanagement, for example—SIB1, SIB2 and SIB9. In an embodiment Table. 2,herein illustrates details regarding the system information read by theMTC device 102 in the 3GPP LTE (Long Term Evolution)—MO use case.

TABLE 2 Read by the Type Description MTC device 102 SIB 1 i) Cell AccessRelated YES Information-PLMN Identity List, PLMN Identity, TA Code, Cellidentity & Cell Status ii) Cell Selection Information - Minimum ReceiverLevel iii) Scheduling Information - SI message type & Periodicity, SIBmapping Info, SI Window length SIB 2 i) Access Barring Information - YESAccess Probability factor, Access Class Baring List, Access Class BaringTime ii)Semi static Common Channel Configuration-Random AccessParameter, PRACH Configuration iii) UL frequency Information - ULEARFCN, UL Bandwidth, additional emission SIB 3 i)Information/Parameters for NO intra-frequency cell reselections SIB 4 i)Information on inter- NO frequency neighboring cells SIB 5 i)Information on inter- NO frequency neighboring cells SIB 6 i)Information for reselection to NO UMTS (UTRAN) cells SIB 7 i)Information for reselection to NO GSM (GERAN) cells SIB 8 i) Informationfor reselection to NO CDMA2000 systems SIB 9 i) Home eNodeB name - forYES future LTE femto cell applications SIB 10 + i) ETWS (Earthquake andYes 11 Tsunami Warning System) Information. SIB 12 i) Commercial MobileAlerting NO System (CMAS) Information.

The MTC device 102 doesn't maintain periodic update related timers, andremove any such procedures. Further, with the context database 103, noDRX related procedures will be applied in the MTC device 102.

In an embodiment, the idle mode is centric only to Ultra-Deep-Sleepmode, where in protocol and physical layer, processor and RF clocks arecompletely shut off and only Ultra-Deep-Sleep mode clock is running tokeep track of Wake up. The Wake up can be interrupted based only, whendevice is interrupted (explicitly triggering the sensor unit of the MTCdevice 102) as a result of data analysis of received data from sensorunit.

In an embodiment, no PAGING channel is designed and configured, i.e.,the MTC device 102 can never wait/poll/interrupt for any notificationfrom the network, when in the Ultra-Deep-Sleep mode trigger of the MOcall does not require man-machine interface (MMI), instead, MO call willbe triggered based on the post analysis of received data from the sensorunit.

The MTC device 102 does not need to perform measurements thereby need ofre-selections could be avoided; moreover, the MTC device 102 can selectthe cell, just before MO operation.

Removal of the DRX and cell re-selection would enable huge power savingin idle mode and UE can go to the Ultra-Deep-Sleep mode and shut off itsmodem/RF/Application processor and could wake up then again based on theimplicit trigger from sensors (sensor unit) and explicit manual trigger.The MTC device 102 can attach only once with the network and negotiateall security, capability and configuration parameters and after that,the MTC device can still remain attached with the network.

FIG. 2b is a flow diagram illustrating a method 200 b of transitioningto a connected mode from an ultra-deep-sleep mode by a MTC device,according to an embodiment as disclosed herein. In an embodiment, atstep 202 b, the method 202 b includes creating the context database 103with the stored temporal parameters, the location parameters and thenetwork parameters acquired for the period of time.

At step 204 b, the method 202 b includes initiating the cell search(cell 104 or neighboring cells 106 and 108.) based on the temporalparameters, the location parameters and the network parameters. At step206 b, the method 202 b includes identifying the cell (cell 104 orneighboring cells 106 and 108.) corresponding to the network parametersin the context database 103 based on the cell search.

At step 208 b, the method 202 b includes initiating the connected modeprocedure with the identified cell. At step 210 b, the method 202 bincludes synchronizing with the cell other than the identified cell(i.e, cell 104).

At step 210 b, the method 202 b includes registering with the cell(other than the identified cell). In an embodiment, whenever the MTCdevice 102 camps on to a new cell other than the cell 104/the cell(s)associated with the context database 103, the MTC device 102, requirescompleting the registration procedure as applied by the networkoperators.

In an embodiment, whenever the MTC device 102 camps on to the cell104/the cell(s) associated with the context database 103, the MTC device102 doesn't require the cell registration, thus faster acquisition ofthe cell can be achieved.

At step 214 b, the method 202 b includes transitioning to the connectedmode with the cell other than the identified cell (i.e., cell 104).

The various actions, acts, blocks, steps, or the like in the flowdiagram 200B may be performed in the order presented, in a differentorder or simultaneously. Further, in some embodiments, some of theactions, acts, blocks, steps, or the like may be omitted, added,modified, skipped, or the like without departing from the scope of theinvention.

FIG. 2c is a flow diagram illustrating a method 200 c of dynamicallyupdating context database, according to an embodiment as disclosedherein.

The steps 202 b-208 b of the FIG. 2b is to be performed for the MTCdevice 102 for the connected mode. Further, at step 202 c, the method200 c includes joining a group created by the cell for scheduling the ULdata through Machine Type Semi Persistence Scheduling-Physical DownlinkControl Channel (M-SPS-PDCCH) interval (as detailed in conjunction withFIGS. 5a-5b ).

At step 204 c, the method 200 c includes identifying the SPS resourcesallocated for particular MTC device 102 within the group. In anembodiment, the method 200 c allows the MTC device 102 to identify theSPS resources allocated for the particular MTC device 102 within thegroup.

At step 206 c, the method 200 c includes transmitting the UL data to thecell 104 in the identified SPS resources. The UL data includes datarelated to metering equipments, data triggered from the sensor unit, orthe like.

At step 208 c, the method 200 c includes estimating the downlink (DL)channel compensation, for e.g, the RFCI, RSRP values of the DL channel.At step 210 c, the method 200 c includes transmitting the UL data whenthe estimated DL channel compensation exceeds a predefined threshold.

The predefined threshold may include the values communicated by thesensor unit, of the MTC device 102, to the cell 104. For example, thesensor unit of the MTC device 102 can detect the use case for MOorigination based on normal or emergency event, and such informationelement whether the MO is for normal or emergency (MO-only,MO-only-emergency) will be shared with the cell 104, during RACHprocedure, which will assist in selecting the best possible scheduler inthe cell 104.

The data allocation can be made dynamic or best-effort (not fairscheduled), when the cell 104 knows type of the MTC device 102initiating the call, and also the type for data transaction (normal oremergency). The MTC device 102 can initiate the MO call, when it assumesthat the channel compensation is minimum (good radio conditions).

The sensor unit information can be used to derive few inferences suchthat, device is static, and also outdoor (light, activity, ambience,wind, location and other such advanced sensors). This can be anadditional optimization in the area of power consumption, since the MTCdevice 102, while moving or indoor device needs to be applyingadditional power to compensate the channel losses. In such cases, thetransmission can be aligning with the “N^(th)” periodic occasion (SPSbased). Therefore, few scheduling occasion will be mute for the MTCdevice 102 in the group. The sensor information can also be sent to cell104 during SPS allocation, so that cell 102 will not schedule the MTCdevice 102 for a specific interval.

Further, when the cell 104 can be configured to (semi-statically)allocate the resources based on the appropriate time when the MTC device102 can perform data transfer based on traffic loads expected duringthat time (analytics for MTC traffic vs. normal traffic at network). Inan embodiment, the cell 104 should inform the wide sense load pattern tothe MTC device 102, which would be quantized further to drive the MINLOAD time, so that “best efforts data” can be align with the cell 104(network) load.

This design specially targeted the use case, where in large number ofMTC devices 102 may try to make the MO call and use the networkresources, which might disturb the normal mobile user traffic especiallyduring peak load hours due to control resources. The control radioresources can be completely occupied by MTC-MO trigger devices, usingvery small part of spectrum, but occupy all control resources and thenetwork cannot schedule the other MTC devices 102. This would result inspectrum fragmentation, where in, spectrum is available but due to lackof control resources, no more addition of device is possible.

The transmission could be aligning with the N^(th) periodic occasion insuch cases. Few scheduling occasion will be muted and for the MTC device102 in a group. The network will inform the MTC device 102 that thenetwork will not schedule the MTC device 102 for “X” number ofscheduling intervals.

Due to the nature of traffic for the MO only MTC devices, for most ofthe scenarios and cases, the MTC device 102 knows the traffic and thedelay tolerance of the traffic data in prior. So the MTC device 102should inform to the network, in dedicated signaling, with threeparameters data size, delay tolerance and type of data. Once all suchinformation is available at the cell 104, then the cell 104 can beconfigured to decide the suitable SPS interval and periodicity based onthe network resource availability, and scheduling priorities.

The cell 104 sends the SPS configuration details in dedicated signalingduring connected mode. The kind of data transfer request (normal oremergency) can be embedded in RACH procedure, so that scheduler can takethe action and choose the appropriate traffic allocation for the MTCdevice 104.

At step 212 c, if the UL data transmission is failed. The method 200 cincludes determining the cell other than the previously identified cell(for e.g., the cell 104) for synchronization and dynamically updatingthe context database 103 with the temporal parameters, the locationparameters and the network parameters.

The various actions, acts, blocks, steps, or the like in the flowdiagram 200C may be performed in the order presented, in a differentorder or simultaneously. Further, in some embodiments, some of theactions, acts, blocks, steps, or the like may be omitted, added,modified, skipped, or the like without departing from the scope of theinvention.

FIG. 3 is a flow diagram illustrating a method 300 for context awarescheduling of resources during emergency condition, according to anembodiment as disclosed herein. The step 302 is performed by MTC device102 and step 304 is performed by the cell 104.

At step 302, the method 300 includes indicating an emergency conditionto the cell 104 (as detailed in conjunction with the FIGS. 6-8).

At step 304, the method 300 includes allocating the UL resources withpredefined conditions. In an embodiment, the predefined conditions aremaximum redundancy, minimum modulation, and time diversity (as detailedin conjunction with the FIGS. 6-8).

The various actions, acts, blocks, steps, or the like in the flowdiagram 300 may be performed in the order presented, in a differentorder or simultaneously. Further, in some embodiments, some of theactions, acts, blocks, steps, or the like may be omitted, added,modified, skipped, or the like without departing from the scope of theinvention

FIG. 4 is a flow diagram illustrating a method 400 for context awarescheduling of resources to at least one MTC device 102 is a group,according to an embodiment as disclosed herein. In an embodiment, atstep 402, the method 400 includes receiving information from a pluralityof the MTC device(s) 102 (referred as (referred as MO-D1, MO-D2, MO-D3,MO-D4, MO-D5, MO-D6 . . . MO-Dn). In an embodiment the informationincludes number of reports generated for the time period and/or averageduration between each generated report.

Further, at step 404, the method 400 includes creating groups (Group 1 .. . Group N) by aggregating each MTC device 102 (MO-D1, MO-D2, MO-D3,MO-D4, MO-D5, MO-D6 . . . MO-Dn) in each of the group based on theinformation.

Furthermore, at step 406, the method 400 includes indicating resourceallocation to at least one MTC device within the group through a MachineType Semi Persistence Scheduling-Physical Downlink Control Channel(PDCCH) (M-SPS-PDCCH) in a M-SPS interval to transmit the UL data to thecell 104 (detailed in conjunction with FIGS. 5a-5b ).

The various actions, acts, blocks, steps, or the like in the flowdiagram 400 may be performed in the order presented, in a differentorder or simultaneously. Further, in some embodiments, some of theactions, acts, blocks, steps, or the like may be omitted, added,modified, skipped, or the like without departing from the scope of theinvention.

The FIGS. 5a-5b illustrates the M-SPS-PDCCH based scheduling ofresources for a group of MTC devices with variable SPS interval,according to an embodiment as disclosed herein. In an embodiment, thegroup of MTC device(s) 102 (the MO-D1, MO-D2, MO-D3, MO-D4, MO-D5, MO-D6. . . MO-Dn) can be scheduled in the semi persistence manner, the SPSresources can be assigned to the group of the MTC device(s) 102/MOdevice (MO-D1, MO-D2, MO-D3, MO-D4, MO-D5, MO-D6) as shown in the FIG.5B. Consequently, the group of the MO devices (MO-D1 . . . MO-Dn) can bescheduled as per the semi persistence manner. For the SPS scheduling,all the MO devices in the group share the same or integer multiple ofscheduling instances with each other i.e., MO-D1 and the MO-D2 havingsame scheduling interval or integer multiple of scheduling interval aregrouped together.

In an embodiment, two category of the MTC-MO only device would emerge,Category-1 devices providing periodic metering information. Such devicesare expected to have almost no mobility. So such devices can inform tothe network about the type of device (Static/Low mobility) whiletriggering initial RACH connection, so that the network can optimize thescheduling.

As a result, the entire context (TA, cell ID, RACH initial power, PUSCHpower, PUCCH power) are known at the coarse level and during theconnection, LTE power control instructions could actually bring finerlevel of power transmission with TPC bits.

Such devices (Category-1) are expected to be attached with the cell 104and always needs the periodic resources from the cell 104. Hence, withinitial connection, the SPS resources can be scheduled with the cell104. The cell 104 can be configured to schedule such devices (MO device,MTC device 102) with defined SPS interval. The SPS scheduling can beconfigured to manage the SPS allocation for various SPS interval basedmechanism (shown in the FIGS. 5a-5b ) followed by contention based RACH(as per the 3GPP).

The MTC device 102/MO devices once attached to the cell 104, can bescheduled based on the SPS scheduling, since all MTC-MO only devices hasa common nature of the periodic reporting. So the MO devices can bescheduled based on the SPS basis for a given scheduling interval and forthe group of the MO devices thereof.

There is a possibility, where, the multiple resources could beunder-utilized in case, if, in the group, a subset of the MO devicesdidn't use the allocated resources due to their periodicity. So theproposed method could be extended with the M-SPS-PDCCH on the top of SPSresources to schedule the subset of the group of the MO devices (asshown in the FIG. 5B).

Moreover, the MO devices can share its type of devices, Traffic class,delay tolerance, type of data. The cell 104 can be configured to drivethe SPS interval based on the above given parameters.

In case, of context specific cell search the MTC device 102 can save theTA, the power head room reporting, the RACH power, the PUSCH power, thePUCCH power. Further, since there is no need to send SR, ACK/NACK, CQI,and feedback due to SPS allocation, hence the MTC device 102 can beconfigured to disable the PUCCH or UL control channel during the MO onlyUL data transfer. Consequently, during a radio bearer reconfiguration,there is no need to allocate the PUCCH channel.

Further, the signaling radio bearer can be established in DL/UL to carryL1/L2/L3 control signaling related to attach and detach Bearerconfiguration and security related signaling. Further, the MTC device102 can remain in semi connected state with the SPS allocation untildetach. Furthermore, the cell 104 should keep the resources allocatedfor MO only devices in the SPS manner.

However, as soon as the MTC device 102 changes the cell 104, the MTCdevice 102 needs to trigger a random accesses procedure, and sincecontext-based resource, allocation will fail.

In an embodiment, the proposed mechanism includes distributing the MOonly devices in time domain such that the MO only devices can bescheduled across the frames and sub-frames. This would distribute theimpact of resource allocation. At every frame or sub-frames there couldbe possibility, where, big number of the SPS resources is allocated.Hence, the M-SPS-PDCCH can be multiplexed on the SPS resources in orderto index, all the MO devices that can be scheduled in thisframe/sub-frame from the allocated groups.

The MTC device 102/MO device with various delay tolerance can beallocated with respective SPS scheduling interval. Each MO device ineach group can share the reporting interval equally to schedulinginstance or integer multiples of scheduling instances.

In an embodiment, the delay tolerance requirement for the set of MOdevices can be scheduled in the same SPS interval. For e.g., Group 1consisting one or more MO devices, wherein each MO device from the groupcan be configured to receive the resources, scheduled in the same SPSinterval as other MO devices in the same group. Similarly various delaytolerance requirement for respective set of MO devices can be scheduled,since the SPS scheduling requires the UL connectivity always, in thatcase, UL sync related operation can be scheduled.

Unlike the conventional systems and methods, where the SPS schedulingmay only involve VoLTE type data communication; transferring the datapackets during the interval (time-interval) scheduled by the SPS, theproposed mechanism introduces the M-SPS-PDCCH scheduling for the MTCdevices.

Unlike the conventional systems and methods, where the SPS scheduling,for e.g., in the VoLTE type data communication, range, time interval,was limited (few seconds), the proposed mechanism provides the range ofthe M-SPS-PDCCH for MTC device for few hours.

In an embodiment, other class of MO devices, Category-2, can be definedas emergency services, where, the communication is expected to be highlyreliable and with minimum latency.

In an embodiment, in case of the network aware scenario by the MTCdevice 102: the Radio logical link entity can be established, by the MTCdevice 102, for the emergency service. Thus, this Radio logical linkentity would be made aware of the emergency nature of the service, andit would set additional bit in the protocol identifier to indicate to NW(in the Scheduling Request or in BSR, as detailed in conjunction withFIG. 8) that the resource allocation request is for emergency services.

Thus, the cell 104 (or, the M-SPS-PDCCH) can be configured to allocatethe UL resources with maximum redundancy and minimum modulation withadditional frequency, time diversity (or Coordinated multipointTransmission resources) at the MTC device 102 side (keeping error rateabove certain thresh hold).

In an embodiment, in case of the network Un-aware scenario, the MTCdevice 102 can be configured to minimize the Sounding reference signal(SRS) power, in order to mimic the path loss, which could have generatedotherwise (for e.g., dummy data shown in FIG. 5B). This would eventuallyforce scheduler to provide resources with maximum protection and minimummodulation with additional time and frequency diversity (transmissionmodes), detailed in conjunction with the FIG. 8.

FIG. 6 is a sequence diagram depicting various signaling messagesbetween the MTC device 102 and the cell 102 for context aware schedulingof resources, according to an embodiment as disclosed herein. Initially,when the MTC device 102 transition to the connected mode from theUltra-Deep-Sleep-Mode, the MTC device 102 triggers random access RACH(602) message to the cell 104, basically the RACH preambles. The cell104 thereupon, in response to the received RACH preambles, can beconfigured to allocate the resources to the UL centric/the MTC device102 thereon transmits the Activation frame no: Radio Bearerreconfiguration (604) message to the MTC device 102.

Thus, the resource allocation can be periodic scheduled based on theM-SPS-PDCCH scheduling (606) whereupon the MTC device 102/each MO devicein the aforementioned group can be configured to transmit the UL data inthe scheduled interval. If the MTC device 102 determines (608) that theUL transmission is running (without failure) then the allocation of theresources can be based on the M-SPS-PDCCH scheduling.

The cell 104, on the other hand can be configured to receive ongoingtraining (610) to develop the context database 103 for the MO device(610). If the MTC device 102/UL centric device in response todetermining (608) the UL transmission failure thereof transmits thesignaling message (612) to the cell 102, the signaling message includingthe update regarding the transmission mode failure (OFF) and therebyswitch back to the normal scheduling operation (SPS as in the VoLTE).

The MTC device 102 can be configured to perform the ongoing search (614)for matching the context from the context database 103. Thus, inresponse to determining that the matching context found (cell found) theMTC therefore re-establish the RACH preambles in order to camp on to thematched cell (to get in to the connected mode).

If the MTC device 102 determines, that no matching cell is found,thereon the MTC device 102 can be configured to perform (618) the 3GPPcell search procedure.

The various steps in the sequence diagram may be performed in the orderpresented, in a different order or simultaneously. Further, in someembodiments, some of the steps may be omitted, added, modified, skipped,or the like without departing from the scope of the invention.

FIG. 7 is a sequence diagram depicting various signaling messagesbetween the MTC device 102 and one or more cells for context awarescheduling of resources, according to an embodiment as disclosed herein,according to an embodiment as disclosed herein. At first, when the MTCdevice 102 transmits the UL data as per the M-SPS-PDCCH schedulinginterval (702) to the cell 102. The MTC device 102 can request tosuspend scheduling (704) for one or more reasons, such as in the lowbattery condition of the MTC device 102, user if the MTC device 102doesn't require the need of the MTC device 102 for time being (voluntaryturns-off), or the like. The request can be transmitted (706) in thePUCCH-1 bit suspend to the cell 104 notifying to stop allocating theresources.

The MTC device 102 again requests (708) to resume scheduling of theresources for transmitting the UL data to the cell 104 and the cell 106.The request can be transmitted (710) in the PUCCH-1 bit resume to thecell 104 and the cell 106.

The MTC device 102 can explore the context database 103 for camping onto the cell (cell 104/cell 106) available in the context database 103.Thus, the M-SPS-PDCCH scheduling other than identified cell (712) can beused for allocating the resources to the MTC device 102.

Any one of the cell 106) (714) can receive the resume indication inresponse to the resume request from the MTC device 102. Thus, the MTCdevice 102 can resume the UL data transmission as per the M-SPS-PDCCHscheduled SPS interval.

Further, the MTC device 102 can be configured to enable the schedulingof the resources for a predefined threshold period of the timer (T). Therequest to suspend scheduling (718) type allocating of the resources forthe “T” period. The request is signaled through the PUCCH-1 bit suspend(720) to the cell 104.

Once the timer exceeds the predefined threshold period (Timer expires)(722) the MTC device 102 can be configured to schedule, M-SPS-PDCCHscheduling (724). Based on the MTC device 102 response only the cell 104(726) can schedule the allocation of resources, for e.g., based on theM-SPS-PDCCH or for example like sending resource request throughexisting 3GPP protocol.

The MTC device 102 determines (728) that the UL transmission is ongoing(NO failure indication detected) the MTC device 102 can be configured tocontinue the transmission of the UL data as per the M-SPS-PDCCHscheduling.

If the MTC device 102 determines (728) that the UL transmission isfailed, thereon the MTC device 102 optionally (730) sends a signalingrequest to the cell 104 indicating transmission mode OFF and switch backto normal scheduling for example like sending resource request throughexisting 3GPP protocol.

The MTC device 102 can be configured to perform the ongoing search (732)for matching the context from the context database 103. Thus, inresponse to determining that the matching context found (734) (cellfound) the MTC device 102 therefore transmits the UL data as per theM-SPS-PDCCH scheduling.

If the MTC device 102 determines, that no matching cell is found,thereon the MTC device 102 can be configured to perform (736) the 3GPPSPS scheduling procedure.

The various steps in the sequence diagram may be performed in the orderpresented, in a different order or simultaneously. Further, in someembodiments, some of the steps may be omitted, added, modified, skipped,or the like without departing from the scope of the invention.

The FIG. 8 is a sequence diagram depicting various signaling messagesbetween the MTC device 102 and the cell 104 for handling emergencyconditions, according to an embodiment as disclosed herein. Once thesensor unit, associated with the MTC device 102, detects the emergencyservices occurrence, the MTC device 102 can transmit the RACH triggered(802) with dedicated, emergency, preamble to the cell 104.

Network aware: The cell 104 upon receiving the dedicated, emergency,preamble from the MTC device 102 can thereof optimize the resourceallocation (for the group of the MO devices) by granting (804) the bestresource allocation available. The transmission mode can be set with theUL TX diversity, least code rate and Min Modulation.

The MTC device 102 can estimate the SRS status of the UL channel and cantransmit the status of the channel (806) to the cell 104. The MTC device102 can set additional bit in the network protocol to inform (808) thenetwork in the scheduling request/in BSR (Buffer Status Report), thatresource allocation are expected for the emergency services.

Thus, as the in the network aware, the cell 104 (810) allocates thegrants (resources) with best resources to the MTC device 102.

Network un-aware: After the MTC device 102, transmit the SRS (UL channelestimation report) (812), the cell 104 minimizes/attenuates (814) theSRS in order to mimic the path loss, which could have generatedotherwise, which eventually force scheduler to provide grant with bestresource allocation (816), with best grant, with maximum protection andminimum modulation with additional time and frequency.

The various steps in the sequence diagram may be performed in the orderpresented, in a different order or simultaneously. Further, in someembodiments, some of the steps may be omitted, added, modified, skipped,or the like without departing from the scope of the invention.

FIG. 9 is a sequence diagram depicting various signaling messagesbetween the MTC device 102 and the cell 104 for handling emergencycondition, according to an embodiment as disclosed herein. As capturedin the use cases, the emergency is directed to particular person(s) andnot to the operator's emergency center, thus MO-only call will alsoconnect with pre-configured MSISDN's and MO-only device can keep sendingdata collected from the sensor unit periodically. During initial attachprocedure, the MTC device 102 can be provisioned with the MSISDN'snumbers to which it would be allowed to make emergency call.

The MTC device 102 can transmit the RACH triggered (902) with dedicated,emergency, preamble to the cell 104. The cell 104 upon receiving thededicated emergency preamble from the MTC device 102 can thereofoptimize the resource allocation (for the group of the MO devices) bygranting (904) the best resource allocation available. The transmissionmode can be set with the UL TX diversity, least code rate and MinModulation.

The MTC device 102 can set additional bit in the network protocol toinform (906) the network in the scheduling request/in BSR (Buffer StatusReport), that resource allocation are expected for the emergencyservices.

The MTC device 102 thus complete (908) the IMS call for VOLTE/VOHSPA/toa configured MSISDN number and keep sending data from the sensor unit.

The various steps in the sequence diagram may be performed in the orderpresented, in a different order or simultaneously. Further, in someembodiments, some of the steps may be omitted, added, modified, skipped,or the like without departing from the scope of the invention.

The embodiments disclosed herein can be implemented through at least onesoftware program running on at least one hardware device and performingnetwork management functions to control the elements. The elements shownin the FIGS. 1 through 9 include blocks which can be at least one of ahardware device, or a combination of hardware device and software units.

The foregoing description of the specific embodiments will so fullyreveal the general nature of the embodiments herein that others can, byapplying current knowledge, readily modify or adapt for variousapplications such specific embodiments without departing from thegeneric concept, and, therefore, such adaptations and modificationsshould and are intended to be comprehended within the meaning and rangeof equivalents of the disclosed embodiments. It is to be understood thatthe phraseology or terminology employed herein is for the purpose ofdescription and not of limitation. Therefore, while the embodimentsherein have been described in terms of preferred embodiments, thoseskilled in the art will recognize that the embodiments herein can bepracticed with modification within the spirit and scope of theembodiments as described herein.

The invention claimed is:
 1. A method of a terminal device, the methodcomprising: performing a cell search in based on a context database, thecontext database including temporal parameters, location parameters andnetwork parameters; identifying a first cell corresponding to thenetwork parameters in the context database based on the cell search; andperforming a connected mode procedure with the identified first cell. 2.The method of claim 1, wherein the method further comprises:synchronizing with a second cell other than the identified first cell;registering with the second cell; and transitioning to a connected mode.3. The method of claim 2, wherein the method further comprises sharingcontext ID, associated with the temporal parameters, the locationparameters and the network parameters, present in the context databaseto the second cell.
 4. The method of claim 3, further comprising:determining a suspend state; and indicating the suspend state to theidentified first cell, wherein the suspend state suspends allocation ofresources for the terminal device.
 5. The method of claim 4, furthercomprising: determining a resume state; determining a current cell wherethe terminal device has to resume; indicating the resume state to thecurrent cell, wherein the current cell is other than the identifiedfirst cell where the terminal device suspended, wherein the contextdatabase is available with all cells present in the context databasethrough internal network message exchange; and receiving the resourcesfrom the current cell.
 6. The method of claim 5, wherein the resumestate is indicated implicitly when a timer is expired and a value of thetimer was indicated in the suspend state to the identified first cell.7. The method of claim 2, wherein the method further comprises: joininga group generated by the identified first cell for scheduling uplink(UL) data; identifying resources allocated for the terminal devicewithin the group; and transmitting UL data to the identified first cellin the identified resources.
 8. The method of claim 7, whereintransmitting the UL data to the identified first cell includes:estimating a downlink (DL) channel compensation; and transmitting the ULdata when the estimated DL channel compensation exceeds a predefinedthreshold.
 9. The method of claim 8, wherein the method furthercomprises: dynamically updating the context database in response todetermining that transmission of the UL data failed; and determining acell other than the identified first cell for synchronization.
 10. Themethod of claim 1, wherein the network parameters comprises a publicland mobile network (PLMN), a Radio Access Technology (RAT), a TimingAlignment (TA), a Uplink (UL) Transmission (Tx) Power, a Physical UplinkShared Channel (PUSCH) power and a Physical Uplink Control Channel(PUCCH) power.
 11. A terminal device, the terminal device comprising: atransceiver configured to communicate with at least one entity; and aprocessor configured to: perform a cell search in based on a contextdatabase, the context database including temporal parameters, locationparameters and network parameters, identify a first cell correspondingto the network parameters in the context database based on the cellsearch, and perform a connected mode procedure with the identified firstcell.
 12. The terminal device of claim 11, wherein the processor furtherconfigured to: synchronize with a second cell other than the identifiedfirst cell; register with the second cell; and transition to a connectedmode.
 13. The terminal device of claim 12, wherein the processor furtherconfigured to share context ID, associated with the temporal parameters,the location parameters and the network parameters, present in thecontext database to the second cell.
 14. The terminal device of claim13, wherein the processor further configured to: determine a suspendstate; and indicate the suspend state to the identified first cell,wherein the suspend state suspends allocation of resources for theterminal device.
 15. The terminal device of claim 14, wherein theprocessor further configured to: determine a resume state; determine acurrent cell where terminal device has to resume; indicate the resumestate to the current cell, wherein the current cell is other than theidentified first cell where the terminal device suspended, wherein thecontext database is available with all cells present in the contextdatabase through internal network message exchange; and control thetransceiver to receive the resources from the current cell.
 16. Theterminal device of claim 15, wherein the resume state is indicatedimplicitly when a timer is expired and a value of the timer wasindicated in the suspend state to the identified first cell.
 17. Theterminal device of claim 12, wherein the processor further configuredto: join a group generated by the identified first cell for schedulinguplink (UL) data; identify resources allocated for the terminal devicewithin the group; and control to the transceiver to transmit UL data tothe identified first cell in the identified resources.
 18. The terminaldevice of claim 17, wherein, in transmission of the UL data to theidentified first cell, the processor configured to: estimate a downlink(DL) channel compensation; and control to the transceiver to transmitthe UL data when the estimated DL channel compensation exceeds apredefined threshold.
 19. The terminal device of claim 17, wherein theprocessor further configured to: dynamically update the context databaseif the UL data transmission is failed; and determine a cell other thanthe identified first cell for synchronization.
 20. The terminal deviceof claim 11, wherein the network parameters comprises a public landmobile network (PLMN), a Radio Access Technology (RAT), a TimingAlignment (TA), a Uplink (UL) Transmission (Tx) Power, a Physical UplinkShared Channel (PUSCH) power and a Physical Uplink Control Channel(PUCCH) power.